Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
Previous Article: Best Practices Series: Make Your Junos Automation Scripts More Robust Next Article: On Box Storage: Option 1 - Flat Files as a Data Store This applies to SLAX version 1.0 and higher
Schafer, Feb 20, 2012 Converting Scripts Between SLAX and XSLT Junos SLAX Scripting Features List SLAX Functions Overview SLAX Best Practices Best Practices Series: Design Considerations for “Long-Lived” On-box SLAX Scripts Best Practices Series: Make Your Junos Automation Scripts More Robust Best Practices Series: Considerations for On-Box Data Storage and Access Examples Written in SLAX https://github.com/Juniper/junoscriptorium SLAX Tools at GitHub https://github.com/Juniper/libslax https://github.com/Juniper/junos-snapshot-administrator A Notepad++ SLAX language module: https://github.com/scottdware/npp-custom-lang Sublime Text package with SLAX snippets: https://github.com/dgjnpr/subl.slax.package SLAX Learning SLAX Scripting Part 1 Learning Byte Video Try SLAX tutorial This Week Book Series Applying Junos OS Automation Mastering Junos OS Automation Programming Junos OS Automation Reference for SLAX 1.0 Open Source libslax ?
Learn what these approaches would look like and the pros and cons of each by reading: Best Practices Series: Design Considerations for “Long-Lived” On-box SLAX Scripts #SLAXbestpractices #How-To
Previous Article: Best Practices Series: Design Considerations for “Long-Lived” On-box SLAX Scripts Next Article: Making Scripts Robust: Checking Status This applies to SLAX version 1.0 and higher. Overview This is the second in a series of best practices intended to reduce the work required to implement your Junos automation, while making the automation more robust and easier to support
Learn techniques for making your scripts run reliably by reading: Best Practices Series: Make Your Junos Automation Scripts More Robust Making Scripts Robust: Checking Status Making Scripts Robust: Handling Routing Engine Switchovers Making Scripts Robust: Recovering from Power Loss or Routing Engine Restart Making Scripts Robust: Managing Retries #junosautomation #Slax #ExpertAdvice
You can find overviews, pros and cons, and "gotchas" for each approach by reading: Best Practices Series: Considerations for On-Box Data Storage and Access On Box Storage: Option 1 - Flat Files as a Data Store On-Box Storage: Option 2 - JUNOS Device Configuration as a Data Store On-Box Storage: Option 3 - Utility MIB as a Data Store On-Box Storage: Option 4 - JUNOS Accounting Files as a Data Store On-Box Storage: Choosing a Solution #JUNOS #Slax #ExpertAdvice #How-To
2 Comments - no search term matches found in comments.
How can I display script results in Junos Space? Best Practices for On-Box Data Storage and Access When you develop an on-box Junos automation, you may need to store some data locally so it can be accessed later by a subsequent instance of your script, a completely different Junos automation, or even a remote application. For expert advice about the pros and cons, and "gotchas" for each data store approach, click: Best Practices Series: Considerations for On-Box Data Storage and Access On Box Storage: Option 1 - Flat Files as a Data Store On-Box Storage: Option 2 - JUNOS Device Configuration as a Data Store On-Box Storage: Option 3 - Utility MIB as a Data Store On-Box Storage: Option 4 - JUNOS Accounting Files as a Data Store On-Box Storage: Choosing a Solution Junos Automation Resources Ansible Automation TechWiki Available Automation tools Chef for Junos OS GitHub repository service J-Net Community page JUISE (Junos OS User Interface Scripting Environment) Juniper Networks Products & Services Juniper Learning Bytes - Configuring CLI Configlets on Junos Space - Junos-Python (PyEZ) Basics - Junos-Python (PyEZ) Installation - SLAX Scripting Part 1 - Using Scripts in Junos Space JUNOScriptorium stored on GitHub Junos Automation Day One Books Junos Automation Scripting Feature Guide Junos PyEZ troubleshooting, auditing, and reporting Junos Space NETCONF (Network Configuration Protocol) Puppet Python and Python Exceptions Ruby and Quickstart Ruby tutorial for Junos Automation SLAX (Stylesheet Language Alternative Syntax) #Python #Slax #Scripting #puppet #juise #JunosSpace #pyez #FAQ #Ruby
Part 2 of 5 of Making Scripts Robust Previous Article: Best Practices Series: Make Your Junos Automation Scripts More Robust Next Article: Making Scripts Robust: Handling Routing Engine Switchovers NOTE: This applies to SLAX version 1.0 and higher
Part 2 of 6 of On-Box Storage Previous Article: Best Practices Series: Considerations for On-Box Data Storage and Access Next Article: On-Box Storage: Option 2 - JUNOS Device Configuration as a Data Store For SLAX version 1.0 and higher, you can pretty much always save data in a flat file of your choosing for your script